<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
    "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://www.w3.org/MarkUp/SCHEMA/xhtml11.xsd"
     xml:lang="en">
  <head>
    <title>Information Center for ARM</title>
    <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=utf-8" />
    <link type="text/css" rel="stylesheet" media="all" href="file://$TOOLKIT_DIR$/doc/infocenter/style/ewic.css" />
  </head>
  <body>
  <div id="topbanner"></div>
  <div id="titlebanner_small">
    <h2>Information Center for ARM</h2>
  </div>
  <div class="breadcrumb"><a href="$TOOLKIT_DIR$/doc/infocenter/index.ENU.html">Information Center for ARM</a> | EXAMPLES</div>
  <div class="mainblock">
   <h2>Example description</h2>

   <pre>  <!--Insert readme.txt-->
     <span style="font-family: monospace;">
################################################################################
#
#                             hello_multicore.eww
#
# $Revision: 32 $
#
################################################################################

DESCRIPTION
===========

  This example project shows how to use the IAR Embedded Workbench for ARM to
  develop and debug a code for Raspberry Pi RP2040. It is intended to demonstrate
  the debugger's multicore capabilities. The source code of the example is part
  of the Raspberry Pi Pico SDK Examples pack and uses Pico SDK version 1.3.0.

  The application launches a function on the second core, printf some messages
  on each core, and pass data back and forth through the mailbox FIFOs.

  The user can switch the debugger view between the RP2040 cores and fully control
  each of them.

  This project includes a second stage bootloader with the following supported
  devices: W25Q080, W25Q16JV, AT25SF081, S25FL132K0
  The required checksum is automatically generated and added at the end of the
  bootloader area during the linking process.

  Debugger wiring connections
  ---------------------------
  The table below considers the ARM20 connector.

  | ARM20      | RPi Pico   |
  | header     | board pad  |
  | ---------- | ---------- |
  | 1          | 3V3        |
  | 4          | GND        |
  | 7          | SWDIO      |
  | 9          | SWCLK      |

  The table below considers the MIPI10/20 connector.

  | MIPI10/20  | RPi Pico   |
  | header     | board pad  |
  | ---------- | ---------- |
  | 1          | 3V3        |
  | 3          | GND        |
  | 2          | SWDIO      |
  | 4          | SWCLK      |

  More information at: https://developer.arm.com/documentation/ka001776/latest

  NOTE:
  -----
  The example project uses an experimental and partial port of Pico SDK for the
  IAR compiler!

  Pico SDK and Pico SDK Examples are distributed under the following licenses:
  https://github.com/raspberrypi/pico-sdk/blob/master/LICENSE.TXT
  https://github.com/raspberrypi/pico-examples/blob/master/LICENSE.TXT

  For the complete Pico SDK:
  https://github.com/raspberrypi/pico-sdk

  For the complete Pico SDK examples:
  https://github.com/raspberrypi/pico-examples


COMPATIBILITY
=============

  By default, the hello_multicore application is configured to run on Raspberry Pi
  Pico board and uses I-Jet debug probe.


CONFIGURATIONS
===============

  Flash Debug:
    Configuration intended for debugging in the QSPI flash memory.


GETTING STARTED
===============

  1) Connect the I-Jet probe to the Raspberry Pi Pico board using "Debugger
     wiring connections" notes in the Description section above.

  2) Start a debug session using the "Download and debug" option. This will
     download the example into the QSPI flash memory.

  3) Open the Terminal I/O window (View -> Terminal I/O).

  4) Run the example. The printf() output by both cores will be displayed in
     the Terminal I/O window.
	   </span>
   </pre>

  </div>
  </body>
</html>






